"Chris Huff" <chr### [at] maccom> wrote in message
news:chrishuff-DDBD75.16570227112000@news.povray.org...
> In article <3a22146e@news.povray.org>, Warp <war### [at] tagpovrayorg>
> wrote:
>
> >   Well, perhaps a 'blur_clock' might be useful, but if I have understood
> > it correctly, it would not fit in the ideology of the motion blur
syntax.
>
> Perhaps, but it seems to confuse people that things outside the
> motion_blur block don't get blurred(Why? I don't know...).

    Well, try rendering the 'Motion Blur.pov' file that I've posted in
povray.text.scene-file - once with motion_blur on and then with motion blur
turned off (just comment out the motion blur line in global_settings{...})
(actually you only need render the first couple of frames each time - the
problem can still be seen clearly). Compare the two results and you'll see
that the motion blurred version is all wrong - the movement of the sphere is
taken into account, but the rotation on the pigment isn't.

    The problem is that you can't do :

#declare foo=
motion_blur {
 pigment {...
}

or even :

motion_blur {
#declare foo=
 pigment {...
}

See ? Of course, in this simple example, if you move the full pigment
definition into the sphere you get correct motion_blur, but what if you have
50000 spheres, all using the foo pigment ?

This is only a very simple example, but it highlights a very annoying
'feature' of MegaPOVs motion_blur implementation.

--
Scott Hill.
Software Engineer.
E-Mail        : sco### [at] innocentcom
PGP Key       : http://pgpkeys.mit.edu:11371
Pandora's Box : http://www.pandora-software.com

*Everything in this message/post is purely IMHO and no-one-else's*

Post a reply to this message